`int/34
string/"hello who are you"

/audivolv/"mime type"/"text/plain"


/internet/com/audivolv/index.html


/"mime type"/default = /string/"text/plain"
/options/volume = /flo/.75

/"regular expression"/examples/evennumberofxs = /"regular expression"/(xx)*

Similar to Ruby, should I include a simpler string syntax that uses single quotes?
Example: /'english sentence'/'This is an example of an english sentence and this is a backslash: \'
Unlike Ruby, I may define the single quote string as having no escapes.
Like Ruby, the double quote strings will have lots of escapes.

/'regular expression'/examples/evennumberofxs = /'regular expression'/(xx)*

Strings will be defined this way:

Single quoted strings can contain any characters except single quote.

Double quoted strings are Java string literals and allow all Java's escape codes.
TODO: How to escape large Unicode chars?


Audivolv syntax is defined this way:

There can be abbreviations, but the simplest and most compatible way to write everything is similar to a unix path. It is a forwardslash delimited path but can not directly contain space (char 33) or any lower char unless its escaped. To contain those, it must be quoted in a string literal, and still go between forward slashes.

Example: /temp/testintvar /op/= /string/"this\r\nis\r\non\r\nfour different lines"/size /op/* /int/3

This 'infix syntax' makes parsing harder. It would be ok if it had a Lisp-like syntax that it is an abbreviation for.

/op/=/call/"/temp/testintvar /op/*/call/\"/string/\\\"this\\\\r\\\\nis\\\\r\\\\non\\\\r\\\\nfour different lines\\\"/size /int/3\""

That is too hard to read. Recursive strings should usually be avoided.

/op/=/call/{/temp/testintvar /op/*/call/{"this\r\nis\r\non\r\nfour different lines"/size /int/3}}

That looks better, but using {} as delimiters will make regular expressions harder to write:
/'regular expression'/(xx){1,3}
It doesnt look like a problem because (xx){1,3} is obviously not (xx)"1,3" because the first char of (xx){1,3} is not {. It is (.

It could also be written as /{'regular expression'}/{{{(xx){1,3}}}}

Are [] better string delimiters? They are also in regular expressions.

The choices for string delimiters are:
[]
()
{}
<>
""
''

/op/=/call/</temp/testintvar /op/*/call/<"this\r\nis\r\non\r\nfour different lines"/size /int/3>>

/temp/testintvar /op/= /string/"this\r\nis\r\non\r\nfour different lines"/size /op/* /int/3

/op/=/call/<
	/temp/testintvar
	/op/*/call/<
		/string/"this\r\nis\r\non\r\nfour different lines"/size
		/int/3
	>
>

/op/=/call/(
	/temp/testintvar
	/op/*/call/(
		/string/(this\r\nis\r\non\r\nfour different lines)/size
		/int/3
	)
)

/op/=/(
	/temp/testintvar
	/op/*/(
		/string/(this\r\nis\r\non\r\nfour different lines)/size
		/int/3
	)
)



/(regular expression)/'(xx)*'

/[regular expression]/(xx)*

/op/=/[/temp/testintvar /op/*/[[this\r\nis\r\non\r\nfour different lines]/size /int/3]]

/'regular expression'/


I like this one best so far:

/op/=/<
	/temp/testintvar
	/op/*/<
		/string/"this\r\nis\r\non\r\nfour different lines"/size
		/int/3
	>
>